Skip to main content

Enterprise Wallet Model



For studios or enterprise teams, it is usually necessary for multiple people to collaboratively manage the wallet. In such cases, the 2-3 architecture is no longer suitable. Due to the typically large amounts involved, absolute decentralization must be ensured, and the preservation of a third Unit becomes an unsolvable problem. Moreover, since multiple people are involved in decision-making, a solution similar to multi-signature is required. Based on this, we have introduced the enterprise wallet, which has the following features:



  1. 2-2 TSS Architecture: 2-2 means that both the user and OpenBlock hold one Unit each, with no third party involved. Signatures must be approved by the user, making it more decentralized.
  2. Equal Rights for Multiple Administrators: The creator can invite multiple administrators to collaboratively manage the wallet. When inviting new administrators, the inviter, the invitee, and OpenBlock will execute an MPC Unit reset, generating a new set of equivalent 2-2 Units. For specific principles, refer to the “Private Key Reset” section. This means each administrator holds a new set of 2-2 Units, ensuring equal rights for everyone, and they can cooperate with OpenBlock to complete signatures.
  3. Support for Regular Members: Administrators hold MPC Units, responsible for approvals and signatures, and can also invite regular members. Regular members only hold public keys and cannot sign, similar to observer wallets. This enriches the wallet’s use scenarios, for example: regular members can be invited to help play games, but any asset transfers in the game must be confirmed by an administrator’s signature, ensuring security and convenience.
  4. Support for Approval Mechanisms: Multiple administrators can configure an m/n approval mechanism. The approval process is centralized, similar to traditional office approval flows. When the last administrator completes the approval, the signature will be completed and recorded on the blockchain simultaneously.
  5. Support for Mutual Backup Recovery: Each administrator must back up their local MPC Unit. If a local Unit is lost, any administrator can assist in recovery, following the same principle as when inviting administrators. For specific details, refer to the “Private Key Reset” section. Thus, multiple administrators act as mutual backups, achieving a multi-signature effect while greatly reducing the risk of private key loss.